Instant messaging interoperability between disparate service providers

ABSTRACT

An apparatus for facilitating instant messaging communications between clients of different instant messaging service provider networks is provided. The apparatus includes translation logic for translating received communications related to an instant messaging service, the received communications associated with an external instant messaging service provider network and formatted according to a secondary protocol. The translation logic translates the received communication from the secondary protocol to a primary protocol, the primary protocol native to a receiving service provider network. The communication may then be routed to a client of the primary network according to the native, primary protocol.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims benefit of priority to previously filed U.S.provisional patent application Ser. No. 60/724,577, filed Oct. 7, 2005,entitled INSTANT MESSAGING INTEROPERABILITY BETWEEN DISPARATE SERVICEPROVIDERS, which is hereby incorporated by reference as if fully setforth herein.

BACKGROUND

1. Field

This relates generally to instant messaging via a network, such as theInternet or an intranet, and in particular, instant messaging betweentwo or more users of disparate instant messaging providers.

2. Description of Related Art

Instant messaging technology generally enables two or more participantsto communicate over a computer network, such as the Internet or aninternet (e.g., a private network), in more or less real time.Typically, each participant uses a client computer system to send andreceive messages (including, e.g., text, voice, files, and the like) viaa user interface. Each client computer in communication is connected viaa network to a common instant messaging service provider and connectionserver. The connection server receives and processes messages fromparticipants, including by forwarding them to the client systems of theother participants for display. The connection server may also beconfigured to send messages on behalf of the system, such as to informparticipants that a fellow participant has disconnected or logged off.

Typically, instant messaging application software is installed at eachclient system to enable the client system to be used as an instantmessaging client. The instant messaging software may be made availablefor download, for example, from a web page accessible via the Internet.A user invokes this software on the client system in order tocommunicate by instant messaging with one or more other participants.The client side application software typically establishes a connectionbetween the client system and the connection server and eitherautomatically logs the user into the connection server or prompts theuser to enter the information necessary to log in, such as a user nameand password. The user may then communicate by means of instantmessaging with one or more other users who are logged into the instantmessaging system at that time.

There are several known instant messaging systems and service providers,such as MSN ® Messenger, Yahoo! ® Messenger, AOL ® Instant Messenger(“AIM”), and the like. Generally, a client using one of the instantmessaging systems is unable to exchange instant messages with a clientusing a different instant messaging system because most instantmessaging services (or service providers) use proprietary solutions. Forexample, a client using MSN ® Messenger may typically communicate withother clients using the same system, e.g., the same instant messagingprovider, but is unable to communicate with clients using other instantmessaging service providers, such as Yahoo! ® Messenger.

Accordingly, it is desirable to allow communication and interoperabilitybetween two or more networks for instant messaging systems. Further, itis desirable to provide presence indicators and buddy list informationfor participants associated with one or more external networks andinstant messaging providers.

SUMMARY

According to one aspect and one example of the present invention, asystem for facilitating instant messaging communication and eventsbetween users of disparate instant messaging service providers isprovided. The system comprises translation logic associated with aprimary instant messenger service provider network operable to translatecommunications received from an external server. In particular, thetranslation logic translates communications received from the externalserver from a secondary protocol to a primary protocol, the primaryprotocol native to the system.

In one example, an apparatus for facilitating instant messagingcommunications between users of different instant messaging serviceproviders includes interface logic and translation logic. The interfacelogic receives communications related to an instant messaging service,the received communications associated with an external instantmessaging service provider network and formatted according to asecondary protocol. The apparatus further includes translation logic fortranslating the received communication from the secondary protocol to aprimary protocol, the primary protocol native to a receiving serviceprovider network.

In some examples, the received communications are received from theexternal instant messaging service provider network (e.g., an externalnetwork client routes the communications to the external network, whichin turn routes the communications to the primary network). Thecommunications may include various instant messaging communications andevents such as subscribe requests, invite requests, unsubscriberequests, watcher notifications, and the like.

Additionally, the apparatus may further include or communicate with oneor more of a gateway event server, event server, SIP gateway, edgeproxy, session manager (e.g., for storing run-time dialog states, SIPdialog routing information, etc.), gateway database (e.g., for storingbuddy lists, persistent information, etc.), connection server,connection manager, and so on.

According to another example, a method for facilitating instantmessaging communications between users of different instant messagingservice providers is provided. In one example, the method includes theacts of receiving a communication related to an instant messagingservice from an external instant messaging service provider network,wherein the received communication is formatted according to a secondaryprotocol, and translating the received communication from the secondaryprotocol to a primary protocol.

According to another example, computer-readable medium comprisinginstructions for facilitating instant messaging communications overdifferent service provider networks is provided. In one example, theinstructions are for causing the performance of a method includingtranslating a communication related to an instant messaging service anddirected to a primary instant messaging service provider network, thereceived communication associated with an external instant messagingservice provider network, where the communication is translated from asecondary protocol to a primary protocol, the primary protocol native tothe primary instant messaging service provider network.

The present invention and its various aspects are better understood uponconsideration of the detailed description below in conjunction with theaccompanying drawings and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 schematically illustrates an exemplary system and environment forcommunication between two instant messaging service providers havingserver-to-server interoperability;

FIG. 2 schematically illustrates an exemplary primary network backendassociated with a first instant messaging provider in communication withan external or secondary network/instant messaging service providernetwork;

FIG. 3 schematically illustrates an exemplary gateway and connectionbetween a primary service provider network backend and an externalnetwork;

FIG. 4 schematically illustrates an exemplary primary network backendassociated with a first instant messaging service provider incommunication with an external or secondary network/instant messagingservice provider;

FIGS. 5-21 illustrate various exemplary communications and event flowsbetween components of a primary network service provider backend incommunication with one or more external networks/instant messagingservice providers; and

FIG. 22 illustrates an exemplary computing system that may be employedto implement processing functionality for various aspects of theinvention.

DETAILED DESCRIPTION

The following description is presented to enable a person of ordinaryskill in the art to make and use the invention. Descriptions of specificdevices, techniques, and applications are provided only as examples.Various modifications to the examples described herein will be readilyapparent to those of ordinary skill in the art, and the generalprinciples defined herein may be applied to other examples andapplications without departing from the spirit and scope of theinvention. Thus, the present invention is not intended to be limited tothe examples described herein and shown, but is to be accorded the scopeconsistent with the claims.

FIG. 1 illustrates an exemplary system and environment in which someaspects described herein may be used. Broadly, a first instant messenger(“IM”) service provider 100 having a plurality of first clients 110logged in, e.g., via a first service provider protocol, and a second IMservice provider 102 having a plurality of second clients 112 logged in,e.g., via a second service provider protocol, are illustrated. The firstand second IM service providers 100, 102 communicate to enable the firstclient 110 to send and receive instant messages with the second client112. In one example, the communication is between the first and secondnetworks 100, 102 directly, e.g., between respective servers or othernetwork components of each network (as opposed to first client 110communicating directly to second network 102 or second client 112communicating directly to first network 100). Such a system may allowfor interoperability between disparate IM providers.

The first and second IM service providers 100, 102 may communicate, atleast in part and in one example, via Session Initiation Protocol(“SIP”) and Session Initiation Protocol for Instant Messaging andPresence Leveraging Extensions (“SIMPLE”) based protocol. SIP/SIMPLE isillustrative of one protocol for intercommunication and interoperabilitybetween a first and second IM service provider for IM and presencefunctionality. Further, SIP/SIMPLE may support server-to-serverinteroperability for voice, video, and the like.

In one example, the specific SIP/SIMPLE protocol for Server-to-ServerInteroperability purposes includes SIP RFC 3261, SIP RFC 3265, and/orPIDF RFC 3863. Additionally, communication between the networks maycommunicate Server-to-Server over TCP with desired levels of securityand IP filtering.

Those of ordinary skill in the art will recognize that various othercommunication protocols (whether open or proprietary) are possible andcontemplated whether used alone or in combination with othercommunication systems/methods. Various modifications may be made to theSIP/SIMPLE protocol depending, for example, on the particular IM serviceproviders and functionality desired. For example, one may modify the anywell known protocol such as SIP/SIMPLE to be used more efficiently(e.g., with respect to transmission speed, process, cost, etc.) within agiven network. Further, other suitable communication protocols such asXMPP or the like that enable or facilitate communication and/orinteroperability between disparate IM providers may be used alone or incombination with the SIP/SIMPLE protocol.

Clients 110 and 112 may include, for example, a user accessing IMaccounts via an internet browser, a personal computer, mobile device,such as a cellular phone or laptop personal computer and the like. Auser is typically connected via a network (such as the Internet or anintranet) to one or more servers including a respective IM serviceprovider for the particular user IM account. The network may furtherinclude various other servers such as a gateway server, proxy server,account server, email server, mobile server, and the like.

A client via a computer device may communicate via a wireless network,such as a wireless gateway, e.g., a cellular, satellite, or otherwireless network. Additionally, the computer device may communicate viaa non-wireless network such as a cable or fiber optic network, or acombination of wireless and non-wireless systems. The computer devicemay include suitable hardware and software, such as a processorconnected to an input device such as a keyboard, a network interface, amemory, and a display. The memory may include logic or software operablewith the device to perform some of the functions described herein. Thedevice may be operable to include a suitable interface for a messagingfacility, such as an email inbox, instant messaging (IM), shortmessaging service (SMS), multimedia messaging service (MMS), and thelike. The device may further be operable to display a web browser foraccessing the Internet or user accounts, including webmail environmentssuch as a Yahoo!® mail account or Hotmail® account, for example.

Networks 100, 102 may be in communication with or include one or moreserver and database systems in communication with one another andcapable of wirelessly communicating with devices of a plurality ofusers. Exemplary server systems may include various routers, databases,gateways, and servers, such as an edge or proxy server, a gatewayserver, a mobile server, email sever, web server, voice messagingserver, and the like. Further, network 20 may include a wireless networkand one or more local area networks (LANs) and/or wide area networks(WAN), such as the Internet, that enables communication between varioususers, devices, servers, agents, modules, clients, processors, and thelike.

In one exemplary operation, a user via client 110 signs-in to theprimary network with a valid ID and password. After a user signs-insuccessfully into the primary network 100, client 110 and/or primarynetwork 110 sends subscriptions for presence/status of buddies that areon the secondary network 102, and sends notifications to the watchers(e.g., client 112 associated with client 110) on the secondary network102 indicating presence/status on the primary network. If a user issigned out of the primary network, appropriate subscription/notificationmessages are sent to the buddies on the secondary network

A user may also block/ignore contacts from the Secondary Network; add anew contact from the Secondary Network by using that contact's ID forthe Secondary Network; delete a contact from the Secondary Network; andrename a contact from the Secondary Network.

FIG. 2 illustrates an overview of an exemplary IM service providernetwork in which some aspects described herein may be used. Not all thecomponents may be required, and variations in the arrangement and typeof the components may be made without departing from the spirit andscope of the various inventions.

In one example, a primary or first network 200 corresponding to a firstIM service provider includes an edge proxy 212. The edge proxy 212 maybe configured for SIP/SIMPLE or other communication protocol(s) usedbetween the first IM service provider and one or more external orforeign networks including one or more IM service providers, such asforeign network 202. In particular, edge proxy 212 provides connectionhandling and routing to the external network(s). The edge proxy 212component is optional, and in other examples the gateway 214 maycommunicate directly to another server or network component (forexample, directly with an edge proxy or gateway of another network).Implementing a generic edge proxy 212, however, may make it easier tofederate with more than one external network. The inclusion of edgeproxy 212 may also help centralize the federation routing and connectionhandling to one or more external networks.

In this example, gateway 214 is the last SIP node into the first networkand proxies clients of the first network as SIP end points to theexternal network(s). Thus, gateway 214 includes logic operable totranslate SIP/SIMPLE communications/events/etc. into native or primaryprotocol communications within the backend of network 200. For example,gateway 214 serves to convert SIP traffic to a native or primaryprotocol for the particular primary network/IM service provider and viceversa. Typically, the scalability limitations of gateway 214 (orequivalent component) are dependent on the performance of a SIP stackimplementation (as described in greater detail with respect to FIG. 3).Additionally, various optimizations may be performed at the SIP layer toimplement batch subscriptions and notifications to improve thescalability depending on the particular network and/or component. In oneexample, gateway 214 is a SIP gateway wherein the SIP stack is optimizedto handle batched Subscriptions and Notifications.

Gateway 216 comprises a gateway event server (ES) and handlescommunication with various backend servers, e.g., the native primarynetwork servers such as reverse buddy event server 218, event server220, and connection server 222. Gateway 216 may also be operable toexport a generic subscription and dialog model that can be used with anytype of external IM/presence protocol. In one example, gateway 216 isfurther stateless and highly scalable.

Gateway 216 may include or access a session manager 242 to store therun-time dialog state, and include or access buddy store 240 for storingthe primary network buddies of external users. The buddy store 240 mayinclude a database substitute for storing the primary account buddies(e.g., Yahoo! buddies, contacts, or the like) of the external users,which may be keyed by the external user address or other identifier, forexample. When subscriptions from the external users come in, they areauthorized against buddy store 240. This may be carried out by SQLimplementations or alternatively replaced by a proprietary database.

The session manager 242 generally stores the transient state of thedialogs. In one example, session manager 242 uses in memory storage, ascalable distributed caching mechanism, but other implementations arepossible.

Additional support from various other servers on the first networkbackend may be included. For example, rbum/rbes 218 may be operable tostore and retrieve external id's in the reverse buddy lists. EventServer (ES) 220 may determine the external domains such that messageswill be appropriately forwarded to the gateway 216 and hence to the SIPgateway 214 (and ultimately to the appropriate external network andexternal user).

FIG. 3 illustrates a block diagram of components of an exemplary gateway300; for example, comprising a SIP/SIMPLE gateway (such as SIP gateway214 shown in FIG. 2). The SIP/SIMPLE gateway comprises a “ConnectionManager” that is operable to handle network I/O with othercomponents/servers on either side of the network (for example, betweenthe external network and the primary network/backend). It may also beoperable for optional transport level security (e.g., encryption,authorization, and the like) and abstracts the transport level detailsfrom other components. The security mechanisms may vary from simple IPfiltering to Mutual Transport Layer Security (MTLS) depending on thetrust level of the component that it is interacting with. In oneexample, highly efficient asynchronous kqueue based I/O may beimplemented for some or all of the network communications. Additionally;the size and behavior of the connection pool can be controlled viaconfiguration parameters.

In one example, the gateway includes SIP stack 300, which may include anOpen source SIP stack, commercial SIP stack, or a proprietary SIP stack.Further, a SIP Abstraction Layer 320, which may be operable to make therest of the gateway implementation agnostic to the SIP stack 310 that isbeing used. A generic set of APIs and objects may provide thisabstraction. As a result, the design is very conducive to adopting acompletely different or modified SIP implementation if desired.

A SIP End Point Presence, Dialog Manager 330 is further included in thisexample. For example, for primary network clients that wish tocommunicate with an external/foreign client (e.g., an MSN client), thiscomponent creates a logical SIP termination point (end point). Thetermination points are created in an on-demand basis, whenever there isan interest from either side of the networks. The SIP SUBSCRIBE andINVITE dialogs attached to each of those termination points are trackedand managed by the dialog manager. The following SIP functionality maybe handled by the SIP End Point Presence, Dialog Manager 330 on-behalfof primary network clients:

-   -   Send/Recv SUBSCRIBE on behalf of the primary network client.    -   Track, manage SUBSCRIBE dialogs (both incoming & outgoing) on        behalf of the primary network client.    -   Send/Process SUBSCRIBE refresh on behalf of the primary network        client.    -   Send/Recv NOTIFY on behalf of the primary network client.    -   Parse and digest PDIF presence information (PDIF: Presence        Information Data Format).    -   Convert the primary network client presence alerts to PDIF        format.    -   Send/Recv INVITE on behalf of the primary network client.    -   Track, manage INVITE dialogs on behalf of the primary network        client.    -   Send/Recv IM on behalf of the primary network client.    -   Send/Recv Typing Notifications on behalf of the primary network        client.    -   Send/Recv UNSUBSCRIBE on behalf of the primary network client.

The SIP end point presence, dialog manager 330 component may furthermaintain its own state information and look-up tables to assist inmapping various SIP dialogs to their corresponding primary networkclient termination points. Additionally, this component may be operableto maintain multiple points of presence (MPOP) or multiple terminationpoints for the same primary network client.

Since there is typically more than one gateway machine running (e.g., onthe primary network), and a given termination point has its associatedstate in only one of the gateway machines, the session manager (e.g.,see FIG. 4) may further help route messages to the appropriate gatewaymachine and vice versa within the network. Appropriate logic may ensurethat the messages are processed in the proper dialog context withoutcompromising the scalability of the system.

Additionally, in this example, the gateway includes a SIP—Native Bridge340. The SIP—Native Bridge 340 generally operates to convert messagesbetween SIP format to the native backend format and vice versa, e.g., toa network native format and vice versa. A primary network, for example,may include servers using relatively fast, centralized state storage,which makes individual machines stateless. Such an architecturegenerally enables seamless clustering/load balancing between theGateways and the primary network servers. The SIP—Native Bridge 340talks to this cluster of primary network servers in the native primarynetwork protocol. It also receives and processes messages fromindividual primary network clients targeted for external networkclients.

FIGS. 4-21 illustrate various exemplary communications and event flowsbetween components of a first network backend in communication with oneor more external networks/instant messaging service providers.

FIG. 4 illustrates an overall architecture of a primary service providernetwork backend including a gateway in communication with an externalnetwork. In this example, an Edge Proxy (EP) 412 is provided for accesscontrol, provisioning, and routing to and from the external network, aswell as for connection pooling and forwarding SIP/SIMPLE messages to andfrom the external network. Generally, the edge proxy 412 is operable andconfigured to communication with one or more domains. Further, a SIPGateway (SGW) 414 operates to proxy primary network clients as SIP endpoints to the external network, map primary network instant messagingrequests into SIP/SIMPLE messages and vice versa. In one example, theSGW 414 relies on a SIP stack (e.g., an Open source SIP stack,commercial SIP stack, or a proprietary SIP stack), and is stateful.Gateway ES (GWES) 416 operates to handle inter-domain gateway requests(mainly IM and presence); bridges SIP Gateway 414 and one or moreprimary network backend servers; GWES 416 is, in one example, statelessand highly scalable.

The architecture further includes a Session Manager (SM) 442 that storesSIP dialog routing information for the backend servers of the primarynetwork. For example, each record is keyed by a primary network clientid, gateway id, and dialog type (IM, presence, etc.), and contains anSGW key pointing to the particular SGW server 414 that holds thecorresponding SIP dialog. The Session Manger server is in memory cachemanagement system, which supports data partition and peer replication.

The gateway DB (GWDB) 440 stores persistent information for externalusers (for example, buddy lists or other information). In one example,MySQL server is used as persistent storage. In one example, the GWDB 440is configured to support data partition and peer replication, but lacksshmproxy such as connection pooling capability.

FIG. 4 illustrates one implementation of exemplary architecture forcommunicating with an external network; however, various otherarchitectures are possible. For example, various components may bedeleted and/or their functionality combined with other components. Asingle gateway device may include logic for performing the functions ofGWES 416 and SGW 414, for example. Additionally, in some examples, edgeproxy 412 may be eliminated or its functionality carried out by anothermachine.

With continued reference to FIG. 4, FIG. 5 illustrates the login of auser to the primary network. Upon login by the user at 1.1, event server(ES) 420 (see FIG. 4) performs the following: For each buddy, ES 420identifies his/her domain and sends this info to the client in prelogindata 1.3. Additionally, upon login 1.3, a notification is sent toexternal users/watchers such as reverse buddies (e.g., from ES server420 to GWES 416 to SGW 414 and to the external network; 2.1-2.2). In oneexample, ES 420 notifies RBES (which may be included within ES 400)about user login and the RBES identifies external users/watchers on theclients reverse buddy list using domain info, and RBES sendsnotification to GWES 416. GWES 416 looks up an SGW key from SM 442,sorts external watchers accordingly, and sends the notification to SGW414. SGW 414 looks up the dialogs for the external watchers in memorycache, and then sends SIP NOTIFY requests to the external network viathe dialogs. If SGW 414 cannot find the dialog for an external watcher,it should send unsubscribe request back to GWES 416 to stop futurenotification.

Additionally, the client subscribes to presence information for externalbuddies (e.g., ES 420 to GWES 416 to SGW 414 to the external network;3.1-3.5). In one example, ES 420 identifies external buddies on theprimary service provider user's buddy list using federation domain info,and sends subscribe request to GWES 416. GWES 416 sends a subscriberequest to SGW 414, and for each external buddy, SGW 414 checks if adialog already exists for the subscription. If so, it sends request toexternal network to refresh the subscription; otherwise it creates a newdialog for the external network buddy, and sends SIP SUBSCRIBE requestto the external network. When SGW 414 gets an ok or error response fromthe external network, it updates or deletes the corresponding cacheddialog, then passes the response to GWES 416. If the response is “ok”,GWES 416 saves the SGW key to SM 442. If the subscription is rejectedwith forbidden error, it means that the external user is no longervalid. GWES 416 may remove the external user from UDB 422 and GWDB 440,and may send notification to the primary network client.

In one example, an initial presence notification may be issued forsuccessfully subscribed external buddies, and may include offlinenotification which can be filtered out by the client (e.g., external network to SGW 414 to GWES 416 to the primary network client; 4.1-4.3). Forexample, an external network sends SGW 414 a notification. If nocorresponding dialog is found, SGW 414 drops the notification; otherwiseit passes the notification to GWES 416. GWES 416 converts thenotification to the primary/native format or protocol, and GWES 416 getstarget connection info from UM 420 and delivers the notification to theprimary network client.

FIG. 6 illustrates exemplary login processes for external users. In thisexample, upon login by an external user, notification is sent to theprimary network watchers (e.g., routed from external network to SGW 414to GWES 416 to primary network client(s); 1.1-1.3). In particular,external network sends online notification to SGW 414 for each primarynetwork watcher. SGW 414 looks up for the corresponding dialog for theprimary network watcher, and if the dialog is not found, SGW 414 willsend an error response to the external network, and the notificationwill not be delivered. If dialog is found, SGW 414 forwards thenotification to GWES 416, where GWES 416 filters, translates, anddelivers the notification to the primary network watcher.

The external user may then subscribe to watch a primary network clientbuddies' presence states (e.g., flowing from the external network to SGW414 to GWES 416; 2.1-2.5). In particular, the external network sends asubscribe request for each primary network buddy. SGW 414 creates dialogfor the subscription and sends subscribe request to GWES 416. GWES 416looks up GWDB 440 to check if the primary network client is on theexternal user's buddy list, and if not, it interprets the request as anAdd Buddy request. If the primary network client is on the buddy listbut pending for approval, GWES 416 sends an ok response followed byoffline notification to SGW 414. If the primary network client is anactive buddy, GWES 416 sends a request to RBES 418 to add the externaluser to the primary network client's reverse buddy list, and thenretrieves the primary network client's initial presence state from UM420, translates the state if needed, and sends it to SGW 414. If SGW 414gets an ok response from GWES 416, it updates the dialog in cache andpasses the response as well as the initial presence state notificationto the external network. If SGW 414 gets error response from GWES 416,it deletes the dialog in cache and sends error response to the externalnetwork.

In some examples and for some network backends, if an external userlogins from multiple locations, the user will send multiplesubscriptions to the primary network. In such instances, SGW 414 maycreate and save multiple dialogs, keyed by the external user id, in itsmemory cache. If later a primary network client buddy sends presencenotification to the external user, the notification will be delivered toeach external location corresponding to the multiple dialogs saved withSGW 414.

FIGS. 7 and 8 illustrate exemplary logoff processes for a primary userand an external user respectively. If the primary network client logsoff, offline notification is sent to external watchers (e.g., from ES418/RBES to GWES 416 to SGW 414 to the external network; 1.1-1.3).Additionally, an unsubscribe process for external buddies' presence isperformed (e.g., from ES 418 to GWES 416; 2.1-2.2). For example, GWES416 looks up SGW keys from SM 442, and passes the request to thecorresponding SGWs 414. It then removes the SGW route record from SM442. SGWs send unsubscribe request to the external network and deletethe corresponding dialogs in its memory cache.

If the external user logs off, offline notification is sent to primarynetwork client watchers (e.g., from the external network to the SGW 414to GWES 416 to primary network clients; 1.1-1.3). Further, anunsubscribe process of primary network clients buddies presence isperformed (e.g., from the external network to SGW 414 to GWES 416 toRBES 418; 2.1-2.2). SGW 414 deletes corresponding dialogs and sends GWES416 an unsubscribe request. GWES 416 removes SGW 414 route from SM 442and removes the external users from the primary network clients buddies'watcher list (i.e., the reverse buddy list).

FIGS. 9 and 10 illustrate processes associated with primary networkclients and external users changing their presence states respectively.In one example, a primary network client changes their presence, whichissues a presence notification. RBES 418 identifies which reversebuddies are from the external network using federation domain info, andsends the notification to GWES 416. The presence notification change isthen sent to the external network for external watchers. In one example,GWES 416 filters or translates the primary network client state into anappropriate external state. GWES 416 looks up SGW key from SM 442 andsends the notification to SGW 414. SGW 414 sends the notification to theexternal network for each existing dialogs; if no dialog is found, itshould send unsubscribe request back to GWES 416 to stop futurenotifications. In one example, if the match between the primary networkclient state and external state is not matched up, the notification isfiltered out (dropped) by GWES 416.

If the external user changes presence state SGW 414 finds correspondingdialog (and may send an error response to the external network if nodialog is found). SGW 414 passes the notification to GWES 416, and GWES416 translates the presence notification to a matching state for primarynetwork client. The primary network may translate a non-matching stateto a native state using a custom message if desired. GWES 416 getstarget connection info from UM 420 and delivers the notification to theappropriate primary network client.

FIGS. 11 and 12 illustrate exemplary processes for users to terminatepresence subscription from users of different providers. For example, inFIG. 11 a primary network client terminates presence subscription froman external user, which may be desirable for spam control or the like.The client request to terminate is handled be GWES 416, which requeststo terminate subscription of an external user. GWES 416 gets externaluser's buddy list from GWDB 440, and GWES 416 sends RBES request toremove external users from the reverse buddy list of each primarynetwork client buddy.

The termination request is then sent to the external user (e.g., fromGWES 416 to SGW 414 to the external network). In one example, GWES 416looks-up SGW key from SM 442 and sends termination request to SGW 414.GWES 416 removes SGW route record from SM 442, and SGW 414 cleans updialogs in its memory cache, and sends termination request to theexternal network. The external network sends offline notification to theexternal user and the external network updates its subscription recordsappropriately. GWES 416 logs the request in its termination log.

Additionally, as shown in FIG. 12, the external network may terminatepresence subscription from a native user. In one example, the SGW 414receives a request to terminate a subscription of a primary networkclient to the presence of an external user. SGW 414 cleans-up dialog inits memory cache and sends a termination request to GWES 416. GWES 416removes route record from SM 442, and GWES 416 sends the primary networkclient offline notification. If the external user already appearsoffline to the primary network client, the primary network client candecide if the notification should be filtered.

FIGS. 13 and 14 illustrate exemplary processes for a native user to addan external buddy. In a first example, FIG. 13, the primary networkclient requests to add an external user as a buddy (e.g., to their buddylist etc.). From the external network an initial offline notification,2.1-2.3 (as a confirmation for subscription triggered by the client'sadd buddy request) is followed by online notification, 3.1-3.3 (thisprocess assumes the external user has approved primary network client'sadd buddy request).

In particular, when the primary network client requests to add theexternal user, ES 418 adds the external user to the primary networkclient's buddy list in UDB and UM 420, and then passes the request toGWES 416 since the new buddy is an external user. GWES 416 then passesthe information to SGW 414 and to the external network to subscribe forthe external user's presence (in the case where the primary networkclient is requesting to add the external user as a buddy). If SGW 414gets ok response from the external network, SGW 414 saves dialog inmemory cache and passes the response to GWES 416. GWES 416 adds theroute record to SM 442, and sends ok response to the primary networkclient. If SGW 414 gets error response from the external network whichindicates that the external id is invalid, SGW 414 deletes thecorresponding dialog and sends error response to GWES 416. GWES 416removes the external user from the primary network client's buddy listin UDB and UM 420 and sends error response to the primary networkclient.

From the external network an offline notification is initially sent as aconfirmation for the subscription request sent (e.g., from SGW 414 toGWES 416 to the primary network client that the external user isoffline). The primary network client may decide whether to drop theinitial offline notification. Finally, from the external network anonline notification (assuming the external user has approved the addbuddy request) that the user is online.

In one example, the external user is added to the primary networkclient's buddy list immediately after getting the ok response from theexternal network for the subscription request. There is no pending stateon the particular configuration of this example since there is no needto detect when the external user accepts/denies the add request.

FIG. 14 illustrates an example where the external users denies the add.The process/event flow is similar to that of FIG. 13 absent the lastseries of events 3.1-3.3 (e.g., absent the external user accepting theadd).

FIGS. 15 and 16 illustrate exemplary processes for adding a primarynetwork client as a buddy for an external user. Generally, the externaluser requests to add the primary network client as a buddy, and theprimary network client approves the add request.

More particularly, the external user requests adding the primary networkclient as a buddy by subscribing to the primary network client'spresence (1.1). SGW 414 sends subscribe request to GWES 416, GWES 416looks up GWDB 440 and detects that this request implies to add a buddy,since the primary network client is not on the external user's buddylist. GWES 416 looks up UDB 420 to check if the primary network clientid is valid. If not, sends error response to external network via SGW414. If the primary network id is valid, GWES 416 sends an ok responseto SGW 414. SGW 414 creates the dialog in cache and passes the okresponse to the external network. In one example, the external user isnotified that the primary network client is offline (e.g., from GWES 416to SGW 414 to the external network). GWES 416 adds route record in SM442, and GWES 416 adds the primary network client to the external user'sbuddy list in pending state in GWDB 440. Finally (e.g., via GWES 416 toCS 420 to the primary network client) approval is requested from theprimary network client.

If the primary network client approves the add request, ES 418 sends addbuddy approval request to GWES 416. GWES 416 changes the primary networkclient buddy's state from pending to active in GWDB 440. GWES 416 sendsupdate request to RBES 418 to add external user to the primary networkclient's reverse buddy list. GWES 416 gets primary network client'sonline state from UM 420 and translates it to external state. Theprimary network client's online presence notification is sent to theexternal user (e.g., via GWES 416 to SGW 414 to the external network anduser).

In GWDB 440, each buddy record contains a state (e.g., active, pending,denied) and a timestamp. The state can be used for various purposes suchas managing add buddy flow, and the timestamp can be used to protectprimary network clients from excessive SUBSCRIBE from an externalnetwork, and may also be used for garbage collection.

FIG. 15 illustrates an example where the primary network client deniesthe add request. The process/event flow is similar to that of FIG. 14absent the last series of events 2.2-2.4. Additionally, event 2.1 is tochange the primary network client's state from “pending” to “denied” onthe external user's buddy list in GWDB 440. In some examples, theexternal network will not notify the external user of the denial event,however, to avoid a request to subscribe each time the external userrelogins, the primary network may keep a denied state associated withthe denied request. Buddy records with denied state can be garbagecollected after certain period of time.

FIGS. 17 and 18 illustrate exemplary processes for deleting a buddy froman external network service provider. In FIG. 17, a primary networkclient deletes an external buddy. In this example, GWES 416 validatesthat the external user is a buddy of the primary network client, andGWES 416 removes the external user from the primary network client'sbuddy list in UDB and UM 420. The primary network client is thennotified of the response to the deleted request (e.g., from GWES 416 toCS 420 to the primary network client a response such as ok, error,etc.). Further, GWES 416 communicates to SGW 414 (and to the externalnetwork) to unsubscribe to the external user's presence and cleans updialog and route records.

In FIG. 18, an external user deleting a primary network client fromtheir buddy list is shown. In this example, the external userunsubscribes to the primary network client's presence. SGW 414 cleans updialog, and SGW 414 sends unsubscribe request to GWES 416. GWES 416removes the route to SGW 414 from SM 442. Further, GWES 416 removes theexternal user from primary network client's reverse buddy list.

FIG. 19 illustrates an exemplary process for starting an IM sessionbetween a primary network client and an external user. In this example,the primary network client initiates an IM session using a primarynetwork client to request to start the IM session with an external user(e.g., the request from the primary network client is communicated fromES 418 to GWES 416). GWES 416 validates the new session. In one example,the system checks if the primary network client does not support sessionbased IM, if so, return error is sent to client, otherwise sends startIM session request to SGW 414. If an IM session dialog already exists,returns ok to GWES 416; if not, sends SIP INVITE request to the externalnetwork.

SGW 414 gets a response from the external network, if the response isok, the session dialog is saved in cache, and otherwise the dialog isdeleted. The SGW 414 further sends response to GWES 416. GWES 416 getsresponse from SGW 414; if response is ok, saves SGW 414 route record inSM and passes the response to primary network client. At this point theprimary network client can send an IM communication.

In examples where the primary network client initiates the IM sessionusing a client that does not support session based IM the process is asfollows. The primary network client sends a first IM to ES 418. ES 418identifies the receiver as an external user (using federation domaininfo or the like), and forwards the request to GWES 416. GWES 416looks-up SM 442 and determines no IM session exists yet for the senderand receiver, so it proceeds to do new session validation (Check YPCminor in this case, for example). If validation fails, an error is sentto the primary network client, otherwise the first IM is sent to SGW414. SGW 414 looks-up cache and finds that no session exists yet, andcaches the IM and sends SIP INVITE request to external user. SGW 414gets response from external user; if session accepted, SGW 414 updatesthe dialog in cache and flush out IM to external, and if the session isrejected, SGW 414 deletes initial dialog in cache and drops the cachedIM, and sends response to GWES 416. GWES 416 gets response from SGW 414if the session is accepted and the SGW 414 saves route in SM 442.

Also shown in FIG. 19 is an example where an external user initiates anIM session with a primary network client. The external network sends SIP1NVTE to SGW 414. If IM dialog already exists for the sender andreceiver (multiple external network clients are running, for example),SGW 414 sends SIP BYE to external user to end the previous session, thensaves the new session dialog to cache. SGW 414 sends start IM request toGWES 416, and GWES 416 validates the new session. For example, GWES 416checks if primary network client id is valid, checks for YPCrestriction, and checks if the primary network client's (receiver's)ignore list. If the validation is ok, GWES saves SGW key in SM andreturns ok to SGW 414; otherwise it sends error to SGW 414. SGW 414checks response from GWES 416, and updates or deletes the initial dialogaccordingly. SGW 414 then sends ok or error response to externalnetwork.

FIG. 20 illustrate exemplary event flows for typing notificationsbetween a primary network client and external user. After the IM sessionis established, IM and typing notification requests can be exchanged.For request coming from the primary network to the external network,GWES 416 looks up SGW key from SM, then sends the request tocorresponding SGW 414 server, which then forwards it to the externalnetwork. For request coming from the external network to the primarynetwork, SGW 414 looks up the corresponding dialog in cache; if dialogis not found, the request will be dropped; otherwise the request will besent to GWES 416, which then deliver it to the appropriate primarynetwork client.

FIG. 21 illustrates event flows for ending an IM session between aprimary network and external user. If the primary network clientterminates the IM session, terminate request is propagated through ES418 to GWES 416 to end the IM session. GWES 416 looks up SGW key from SM442, sends the request to SGW 414, and deletes SGW route record from SM442. SGW 414 deletes the dialog in cache, and sends SIP BYE to theexternal user to end the session.

If the external user ends an IM session, the external user sends a SIPBYE to SGW 414. SGW 414 deletes the dialog in cache and sends end IMsession request to GWES 416. GWES 416 deletes SGW route record in SM.Further, GWES 416 may send the primary network client an end IM sessionrequest.

FIG. 22 illustrates an exemplary computing system 600 that may beemployed to implement processing functionality for various aspects ofthe invention (e.g., as a gateway server or machine). Those skilled inthe relevant art will also recognize how to implement the inventionusing other computer systems or architectures. Computing system 600 mayrepresent, for example, a desktop, mainframe, server, client, or anyother type of special or general purpose computing device as may bedesirable or appropriate for a given application or environment.Computing system 600 can include one or more processors, such as aprocessor 604. Processor 604 can be implemented using a general orspecial purpose processing engine such as, for example, amicroprocessor, microcontroller or other control logic. In this example,processor 604 is connected to a bus 602 or other communication medium.

Computing system 600 can also include a main memory 608, preferablyrandom access memory (RAM) or other dynamic memory, for storinginformation and instructions to be executed by processor 604. Mainmemory 608 also may be used for storing temporary variables or otherintermediate information during execution of instructions to be executedby processor 604. Computing system 600 may likewise include a read onlymemory (“ROM”) or other static storage device coupled to bus 602 forstoring static information and instructions for processor 604.

The computing system 600 may also include information storage mechanism610, which may include, for example, a media drive 612 and a removablestorage interface 620. The media drive 612 may include a drive or othermechanism to support fixed or removable storage media, such as a harddisk drive, a floppy disk drive, a magnetic tape drive, an optical diskdrive, a CD or DVD drive (R or RW), or other removable or fixed mediadrive. Storage media 618 may include, for example, a hard disk, floppydisk, magnetic tape, optical disk, CD or DVD, or other fixed orremovable medium that is read by and written to by media drive 614. Asthese examples illustrate, the storage media 618 may include acomputer-readable storage medium having stored therein particularcomputer software or data.

In alternative embodiments, information storage mechanism 610 mayinclude other similar instrumentalities for allowing computer programsor other instructions or data to be loaded into computing system 600.Such instrumentalities may include, for example, a removable storageunit 622 and an interface 620, such as a program cartridge and cartridgeinterface, a removable memory (for example, a flash memory or otherremovable memory module) and memory slot, and other removable storageunits 622 and interfaces 620 that allow software and data to betransferred from the removable storage unit 618 to computing system 600.

Computing system 600 can also include a communications interface 624.Communications interface 624 can be used to allow software and data tobe transferred between computing system 600 and external devices.Examples of communications interface 624 can include a modem, a networkinterface (such as an Ethernet or other NIC card), a communications port(such as for example, a USB port), a PCMCIA slot and card, etc. Softwareand data transferred via communications interface 624 are in the form ofsignals which can be electronic, electromagnetic, optical, or othersignals capable of being received by communications interface 624. Thesesignals are provided to communications interface 624 via a channel 628.This channel 628 may carry signals and may be implemented using awireless medium, wire or cable, fiber optics, or other communicationsmedium. Some examples of a channel include a phone line, a cellularphone link, an RF link, a network interface, a local or wide areanetwork, and other communications channels.

In this document, the terms “computer program product” and“computer-readable medium” may be used generally to refer to media suchas, for example, memory 608, storage device 618, storage unit 622, orsignal(s) on channel 628. These and other forms of computer-readablemedia may be involved in providing one or more sequences of one or moreinstructions to processor 604 for execution. Such instructions,generally referred to as “computer program code” (which may be groupedin the form of computer programs or other groupings), when executed,enable the computing system 600 to perform features or functions ofembodiments of the present invention.

In an embodiment where the elements are implemented using software, thesoftware may be stored in a computer-readable medium and loaded intocomputing system 600 using, for example, removable storage drive 614,drive 612 or communications interface 624. The control logic (in thisexample, software instructions or computer program code), when executedby the processor 604, causes the processor 604 to perform the functionsof the invention as described herein.

It will be appreciated that, for clarity purposes, the above descriptionhas described embodiments of the invention with reference to differentfunctional units and processors. However, it will be apparent that anysuitable distribution of functionality between different functionalunits, processors or domains may be used without detracting from theinvention. For example, functionality illustrated to be performed byseparate processors or controllers may be performed by the sameprocessor or controller. Hence, references to specific functional unitsare only to be seen as references to suitable means for providing thedescribed functionality, rather than indicative of a strict logical orphysical structure or organization.

Although the present invention has been described in connection withsome embodiments, it is not intended to be limited to the specific formset forth herein. Rather, the scope of the present invention is limitedonly by the claims. Additionally, although a feature may appear to bedescribed in connection with particular embodiments, one skilled in theart would recognize that various features of the described embodimentsmay be combined in accordance with the invention.

Furthermore, although individually listed, a plurality of means,elements or method steps may be implemented by, for example, a singleunit or processor. Additionally, although individual features may beincluded in different claims, these may possibly be advantageouslycombined, and the inclusion in different claims does not imply that acombination of features is not feasible and/or advantageous. Also, theinclusion of a feature in one category of claims does not imply alimitation to this category, but rather the feature may be equallyapplicable to other claim categories, as appropriate.

Although the present invention has been described in connection withsome embodiments, it is not intended to be limited to the specific formset forth herein. Rather, the scope of the present invention is limitedonly by the claims. Additionally, although a feature may appear to bedescribed in connection with a particular embodiment, one skilled in theart would recognize that various features of the described embodimentsmay be combined in accordance with the invention. Moreover, aspects ofthe invention describe in connection with an embodiment may stand aloneas an invention.

Moreover, it will be appreciated that various modifications andalterations may be made by those skilled in the art without departingfrom the spirit and scope of the invention. The invention is not to belimited by the foregoing illustrative details, but is to be definedaccording to the claims.

1-30. (canceled)
 31. An apparatus comprising a processor and memory, thememory storing processor-executable logic comprising: interface logicthat receives, at a stateless gateway server comprised within a primaryservice provider network, a communication for a client of the primaryservice provider network from at least one of a plurality of externalinstant messaging service provider networks, wherein the receivedcommunication is received in a secondary protocol associated with anexternal instant messaging provider network transmitting thecommunication; translation logic that translates, at the statelessgateway server, the received communication from the secondary protocolto a primary protocol, the primary protocol native to the primaryservice provider network and the primary protocol being different fromthe secondary protocol; and presence data management logic that creates,at the stateless gateway server, for the client of the primary serviceprovider network, a plurality of logical termination points thatfacilitate direct communication between the client of the primaryservice provider network and respective ones of the plurality ofexternal instant messaging service provider networks.
 32. The apparatusof claim 31, wherein the received communication comprises at least oneof a subscribe request, an invite request, or an unsubscribe request.33. The apparatus of claim 31, the processor-executable logic furthercomprising: and logic that translates a communication to be sent to theexternal instant messaging service provider from the primary protocol tothe secondary protocol; and logic that transmits the communicationtranslated to the secondary protocol to the external instant messagingservice provider.
 34. The apparatus of claim 33, wherein the sentcommunication comprises at least one of a notification to watchers, asubscribe request, an invite request, or an unsubscribe request.
 35. Theapparatus of claim 31, the memory further comprising: a session manageras a centralized storage, the session manager storing informationcomprising a dialog state associated with the received communication.36. The apparatus of claim 31, the memory further comprising: aconnection manager that processes the received communication, whereinthe connection manager includes an end point present dialog manager. 37.The apparatus of claim 31, the processor-executable logic furthercomprising logic for: using a session manager as the centralizedstorage, the session manager storing information comprising a dialogstate associated with the received communication.
 38. The apparatus ofclaim 31, the memory further comprising: a buddy store that storesprimary network buddies of external users, wherein the primary networkbuddies are associated with the receiving service provider network andthe external users are associated with the external instant messagingservice providers.
 39. A method comprising: receiving, at the statelessgateway server comprised within a primary service provider network, acommunication related to an instant messaging service for a client ofthe primary service provider network from at least one of a plurality ofexternal instant messaging service provider networks, wherein thereceived communication is formatted according to a secondary protocolassociated with the external instant messaging service provider networktransmitting the communication; translating, at the stateless gatewayserver, the received communication from the secondary protocol to aprimary protocol, the primary protocol native to the primary serviceprovider network and the primary protocol is different than thesecondary protocol; and creating, by the stateless gateway server, forthe client of the primary service provider network, a plurality oflogical termination points that facilitate direct communication betweenthe client of the primary service provider network and respectiveclients of the plurality of external instant messaging service providernetworks.
 40. The method of claim 39, wherein the received communicationcomprises at least one of a subscribe request, an invite request, or anunsubscribe request.
 41. The method of claim 39, further comprising:causing, by the stateless gateway server, a communication related toinstant messaging service to be sent to the external instant messagingservice provider network, the communication being sent according to thesecondary protocol.
 42. The method of claim 38, further comprising:routing, by the stateless gateway server, the translated communicationto the client of the primary network according to the primary protocol.43. The method of claim 38, further comprising: using, by the statelessgateway server, a session manager as the centralized storage, thesession manager storing information comprising a dialog state associatedwith the received communication.
 44. A computer-readable non-transitorystorage medium comprising computer-readable instructions for: receiving,at a stateless gateway server computer comprised within a primaryinstant messaging service provider network, a communication related toan instant messaging service for a client of the primary serviceprovider network from one of a plurality of external instant messagingservice provider networks, wherein the received communication isformatted according to a secondary protocol associated with the externalinstant messaging service provider network transmitting thecommunication; translating, at the stateless gateway server, thereceived communication from a secondary protocol to a primary protocol,the primary protocol native to the primary instant messaging serviceprovider network and the primary protocol is different than thesecondary protocol; and creating, by the stateless gateway server, forthe client of the primary instant messaging service provider network,respective logical termination points that facilitate directcommunication between the client of the primary service provider networkand the plurality of external instant messaging service providernetworks.
 45. The computer-readable non-transitory storage medium ofclaim 44, wherein the received communication comprises at least one of asubscribe request, an invite request, or an unsubscribe request.
 46. Thecomputer-readable non-transitory storage medium of claim 44, furthercomprising instructions for: causing, by the stateless gateway server, acommunication related to the instant messaging service to be sent,wherein the communication is sent according to the secondary protocol.47. The computer-readable non-transitory storage medium of claim 44,further comprising instructions for: routing, by the stateless gatewayserver, the translated communication to the client of the primaryinstant messaging service provider network.
 48. The computer-readablenon-transitory storage medium of claim 44, further comprisinginstructions for: using, by the stateless gateway server, a sessionmanager as the centralized storage, the session manager storinginformation comprising a dialog state associated with the receivedcommunication.